Skip to content

Fix cloud-init logging format#441

Merged
aramprice merged 1 commit into
cloudfoundry:ubuntu-jammyfrom
s4heid:cloud-init-log-cfg
Oct 2, 2025
Merged

Fix cloud-init logging format#441
aramprice merged 1 commit into
cloudfoundry:ubuntu-jammyfrom
s4heid:cloud-init-log-cfg

Conversation

@s4heid

@s4heid s4heid commented Sep 25, 2025

Copy link
Copy Markdown
Contributor

The typo leads to problems when cloud-init attempts to load the logging configuration. This is evident in the daemon logs, as shown by the following stack trace:

cloud-init[515]: 2025-09-24 12:07:29,260 - util.py[WARNING]: Failed
loading yaml blob. Invalid format at line 10 column 1: "expected
? '', but found ''
cloud-init[515]: in "", line 10, column 1:
cloud-init[515]: _log:
cloud-init[515]: ^"

Note

For comparison, the upstream config has the correct format.

The typo leads to problems when cloud-init attempts to load the logging
configuration. This is evident in the logs, as shown by the following
stack trace:

> cloud-init[515]: 2025-09-24 12:07:29,260 - util.py[WARNING]: Failed
>   loading yaml blob. Invalid format at line 10 column 1: "expected
?   '<document start>', but found '<block mapping start>'
> cloud-init[515]:   in "<unicode string>", line 10, column 1:
> cloud-init[515]:     _log:
> cloud-init[515]:     ^"
@github-project-automation github-project-automation Bot moved this from Inbox to Pending Merge | Prioritized in Foundational Infrastructure Working Group Oct 2, 2025
@aramprice
aramprice merged commit d48b580 into cloudfoundry:ubuntu-jammy Oct 2, 2025
2 checks passed
@github-project-automation github-project-automation Bot moved this from Pending Merge | Prioritized to Done in Foundational Infrastructure Working Group Oct 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants